[% setvar title RFCs %]
<div id="archive-notice">
    <h3>This file is part of the Perl 6 Archive</h3>
    <p>To see what is currently happening visit <a href="http://www.perl6.org/">http://www.perl6.org/</a></p>
</div>
<div class='pod'>
<a name='RFCs'></a><h1>RFCs</h1>
<p>Larry Wall will decide the changes to make for perl6 based on our
suggestions.  To make life easy for him, we should put some effort
into our suggestions.  RFCs are intended to be focus discussion on
something that will be useful to Larry when he makes his decisions.</p>
<p>This format was last changed July 31, 2000.</p>
<a name='Format'></a><h1>Format</h1>
<p>RFCs are written in POD.  <i><a href='http://search.cpan.org/perldoc?rfc-sample.pod'>rfc-sample.pod</a></i> is a sample.  The
important sections are: TITLE, VERSION, ABSTRACT, DESCRIPTION,
IMPLEMENTATION, and REFERENCES.  An optional section is STATUS.</p>
<p>A description of each section follows:</p>
<a name='TITLE'></a><h2>TITLE</h2>
<p>One line, describing the proposed new feature or change.</p>
<a name='VERSION'></a><h2>VERSION</h2>
<p>Metadata information: Maintainer, Date, Version, Mailing List, and
Number.</p>
<ul>
<li><a name='Maintainer. The name and email address of the person currently maintaining the RFC.'></a>Maintainer.  The name and email address of the person currently
maintaining the RFC.</li>
<li><a name='Date. The date of the most recent release.'></a>Date.  The date of the most recent release.</li>
<li><a name='Version. An integer version number. First version is 1.'></a>Version.  An integer version number.  First version is 1.</li>
<li><a name='Mailing List. The mailing list on which discussion about this feature or change has taken place.'></a>Mailing List.  The mailing list on which discussion about this feature
or change has taken place.</li>
<li><a name='Number. Unique RFC number, assigned by the librarian.'></a>Number.  Unique RFC number, assigned by the librarian.</li>
</ul>
<p>Here is an example:</p>
<pre>  =head1 VERSION

    Maintainer: Nathan Torkington &lt;<a href='mailto:gnat@frii.com'>gnat@frii.com</a>&gt;
    Date: 30 Jul 2000
    Version: 2
    Mailing List: perl6-internals
    Number: 1</pre>
<a name='ABSTRACT'></a><h2>ABSTRACT</h2>
<p>One or two paragraph summary of the problem and proposed solutions,
or feature and probable implementations.</p>
<a name='DESCRIPTION'></a><h2>DESCRIPTION</h2>
<p>Detailed discussion of the problem or new feature.</p>
<a name='IMPLEMENTATION'></a><h2>IMPLEMENTATION</h2>
<p>Discussion of the possible implementations.  This doesn't have to
be completely defined down to the <code>char *</code>, instead enough to show
that it can be done.</p>
<a name='REFERENCES'></a><h2>REFERENCES</h2>
<p>A list of pointers to other documentation relevant to the topic.  This
could be other RFCs, internet standards, existing Perl or
operating-system documentation, books, and so on.</p>
<a name='STATUS'></a><h2>STATUS</h2>
<p>Once an RFC is retired, the STATUS section is used to say why and how
the RFC is dead.</p>
<a name='Submitting'></a><h1>Submitting</h1>
<p>Mail the RFC to <code>perl6-rfc@perl.org</code>.  It will be assigned a
number if it doesn't already have one, then posted to the
<code>perl6-announce</code> mailing list, as well as the list in the <code>Mailing
list</code> metadata.  They will also be archived at <code><a href='http://dev.perl.org' target='_blank'>dev.perl.org</a></code>.</p>
</div>
